-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Smooth transition for Container Registry enable switch #2881
Conversation
Your org requires the Graphite merge queue for merging into mainAdd the label “flow:merge-queue” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge. Or use the label “flow:hotfix” to add to the merge queue as a hot fix. You must have a Graphite account and log in to Graphite in order to use the merge queue. Sign up using this link. |
Coverage report for
|
St.❔ |
Category | Percentage | Covered / Total |
---|---|---|---|
🔴 | Statements | 5.27% | 395/7491 |
🔴 | Branches | 4.57% (-0% 🔻) |
237/5184 |
🔴 | Functions | 3.16% | 78/2471 |
🔴 | Lines | 5.19% | 380/7323 |
Test suite run success
124 tests passing in 14 suites.
Report generated by 🧪jest coverage report action from c285c0c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Merge activity
|
Resolve #2880 **Changes:** Updates the container registry list fetch behavior to use different Apollo fetch policies based on whether it's the initial fetch or a subsequent reload: - Initial fetch uses `store-and-network` to show cached data while fetching fresh data - Subsequent fetches use `network-only` to ensure fresh data **Rationale:** This change optimizes the user experience by showing cached data immediately on first load while still ensuring up-to-date data on manual refreshes.
17b46f7
to
c285c0c
Compare
Resolve #2880
Changes:
Updates the container registry list fetch behavior to use different Apollo fetch policies based on whether it's the initial fetch or a subsequent reload:
store-and-network
to show cached data while fetching fresh datanetwork-only
to ensure fresh dataRationale:
This change optimizes the user experience by showing cached data immediately on first load while still ensuring up-to-date data on manual refreshes.